@Donahue said in Security Updates Not Listening to Times.:

@WrCombs said in Security Updates Not Listening to Times.:

@Donahue said in Security Updates Not Listening to Times.:

@WrCombs said in Security Updates Not Listening to Times.:

@Donahue said in Security Updates Not Listening to Times.:

@WrCombs said in Security Updates Not Listening to Times.:

5:30-6:00 pm and he manually restarts everything and then everything works fine.
Right now I

So for us following along at home, what was the actual problem and what was the fix? It looks like you were saying that the MSE updates were running at 5:30 or whenever, but was it actually trying to run a scan at that time? Was that the actual cause of the slowdowns?

The problem was that MSE was installing updates daily at 5-5:30 causing the Point of Sale that runs off of that PC to freeze and lock up until they were restarted.
The fix?
I excluded our application directory from MSE updates and havent had a problem in 3 days.
I have checked and the updates are still coming in , but no system lock ups.

I don't see the correlation. How is excluding a directory from updates even a thing? I can see excluding a directory from a scan, but MSE doesn't get updates based on directories.

This is what I know : okay? Stay with me here;

My terminals on the front of house were locking up every time a Security Update came through on my Back office PC. Causing the Site to have to restart the terminals manually every time at the same time, Daily.

After excluding the Directory for my application, I haven't had an issue in 3 days, and counting at multiple of my Windows 7 Sites.

Could it be that the updates were spinning up more RAM to install these updates?

Could it be that The System was False Positive hitting as @Dashrender suggested?

I wonder if it wasn't also running a scan at the same time using the newly installed updates? That is the only thing that makes sense. I wont argue with the results, I was just not satisfied with the explanation, because I couldn't follow the logic.

I tend to agree that a scan must be happening - otherwise updates alone shouldn't affect the operation of the PC.

after restoring to my first point i've created before ... able to update sp1 succesfully .
solved now by me ...

Updated with 1903

Good tip had someone on the phone last week saying their number lock wasn't staying on after reboots

@wrcombs said in File Sharing:

What Fixed this issue:
I downloaded : Mspsvc.reg
and BFE.Reg

After download : Right click and select merge
repeat with second file,
Restart PC

the advanced sharing settings were set correctly.
Shared the file and Watch the Point of sale start up as normal.
Thanks for all the help.

As I said offline, the Firewall service needed to be offline for it to work unfortunately.

@wrcombs said in Cant communicate:

@obsolesce said in Cant communicate:

@dafyre said in Cant communicate:

Glad you got it, but my money is on a b0rk3d windows update that broke it.

It's Windows XP... those don't get updates anymore.

the back office was Windows 7. . . . Isnt windows 7 still receiving security updates?

Yes, it's still widely deployed. But freaking ancient.

You see! This is why you shouldn't patch!

I've have used that ProfileWiz before by ForensiT, works really well.

@jaredbusch said in Anyone have a powershell line to create a new admin account:

I have a handful of Windows 7 machiens not on a domain.

I want to put a new Admin account on them.

The current user accounts have admin rights, which I will remove, I have ScreenConnect installed and running with admin perms. So I can pop a powershell via the ScreenConnect command window easily to do this.

not tested... maybe this thread can help with PS 2.0. Quoting code here:

# Create new local Admin user for script purposes $Computer = [ADSI]"WinNT://$Env:COMPUTERNAME,Computer" $LocalAdmin = $Computer.Create("User", "LocalAdmin") $LocalAdmin.SetPassword("Password01") $LocalAdmin.SetInfo() $LocalAdmin.FullName = "Local Admin by Powershell" $LocalAdmin.SetInfo() $LocalAdmin.UserFlags = 64 + 65536 # ADS_UF_PASSWD_CANT_CHANGE + ADS_UF_DONT_EXPIRE_PASSWD $LocalAdmin.SetInfo()

Oh, wait, it's Friday afternoon.

@dustinb3403 said in Cross Post - Restoring Windows 7 Image Without a Repair disk or Installation Media:

@Dashrender

@ezacal said in Cross Post - Restoring Windows 7 Image Without a Repair disk or Installation Media:

@dustinb3403 I appreciate the recommendation of alternate imaging software and i personally would love to use them but my mission is to get the VHDs stored in the windows image to transfer over directly to a blank HDD, no matter the method used the windows image must be the source of the restoration.

This is the issue here. He is stating he must use Windows Recovery to restore the operating system.

Not sure of why or what requirement this is other than

@ezacal said in Cross Post - Restoring Windows 7 Image Without a Repair disk or Installation Media:

@dustinb3403 ah yes i neglected to mention we are able to clone the drive via clonezilla but a lot of the times the users have to continue work while we send out a new drive, so as of now i only have a windows image to work with, with the constraint of not being able to use a repair disk

Where he says the users have to be able to use their systems.

Which the answer to this is an Agent based backup solution (Veeam Endpoint, UrBackup etc) can all write to remote storage and can be written to new drives that then get sent out to the user to physically remove the hard drive from their system to install this "restored image".

There are potential issues with this. Restoring a computer image that's 3 months old could easily find a situation where the restore has a different computer password with the network, etc.

Around that time is when we started to find Nethserver to be the more interesting project.

And Nethserver is active here, whereas Zentyal is not.

Guest additions are a big deal. It should have sped up considerably after you installed them.

This person had the same issue, see below:
https://www.tenforums.com/general-support/59759-strange-issues-after-anniversary-update.html

The AISuite 3 with Asus causes this. Just make sure to uninstall or start WIndows without any of the additional startup programs or services enabled.

https://www.theregister.co.uk/2017/04/13/microsoft_kills_support_old_windows_on_new_chips/

My answer to the OP. I mean I am not saying MS is good or bad, or Linux OS's are good or bad. But the OP was just a whiny bitch.

0_1489771473077_upload-b9cb86b3-5bb0-409a-bbe8-3b4008d3a94f

@JaredBusch said in Windows Update Error 0x800B0100:

@nadnerB said in Windows Update Error 0x800B0100:

I have been patching Windows 7 machines that haven't been turned on for a few months and have found that the update process takes an age of man to complete without manual intervention. (local WSUS)

Fortunately, I have found a process that's worked to speed up the update process.

Download and Install the latest Windows Update Agent
-- here: https://support.microsoft.com/en-au/kb/949104 Run MS Windows Update Diagnoistic tool
-- here: https://support.microsoft.com/en-us/kb/2714434 Install Windows6.1-KB3172605-x64 (post install reboot required)
-- here: https://www.microsoft.com/en-us/download/details.aspx?id=53332 run wuauclt /r /a

That is way too intense on IT staff time.

Click check for updates. Close window and tell user to work like normal. Next morning, click install. Close window and tell user to work like normal and when it pops up to reboot, do so.

Way less IT time involved.

Yes, this is true but it can be done while doing other things on the PC. You know, multitasking 😉

@travisdh1 said in Windows 7 and 8.1 updates switching to cumulative monthly rollups starting in October:

@scottalanmiller said in Windows 7 and 8.1 updates switching to cumulative monthly rollups starting in October:

I've seen a lot of people complaining that there have so many small patches break things that this will cause support problems for them.

I should pull the local repair shop owners in here, you'd never hear the end of it.

Ha! Yeah, why do patch updates only seem to affect consumers and SMBs?